…cycle

Users need guardrails to be obvious and repeatable on every task, not just first-run setup. This change makes setup/init surfaces explicitly teach and preserve the same branch->lock->PR/merge->cleanup loop, and introduces an init alias so teams can bootstrap with either command.

Constraint: Existing setup behavior and template install paths must remain backward compatible
Rejected: Hook-only enforcement without AGENTS/prompt updates | users still miss the workflow contract in agent instructions
Confidence: high
Scope-risk: moderate
Reversibility: clean
Directive: Keep setup prompt text, README checklist, and AGENTS template lifecycle rules aligned whenever workflow steps change
Tested: node --check bin/multiagent-safety.js
Tested: node --test --test-name-pattern="setup provisions workflow files and repo config" test/install.test.js
Tested: node --test --test-name-pattern="init aliases setup and provisions workflow files" test/install.test.js
Tested: temp repo bootstrap via node bin/multiagent-safety.js init --target <tmp-repo> --no-global-install with AGENTS loop assertions
Tested: node bin/multiagent-safety.js copy-prompt | rg "gx init|For every new user message/task"
Not-tested: full npm test remains noisy in this environment due pre-existing broad install/fuzz test instability unrelated to this change